Here are some suggested adjustments:
To assure a spawned NetworkObject persists after the owner leaves a session, set the NetworkObject.DontDestroyWithOwner property to true. This assures the client-owned NetworkObject doesn't get destroyed when the owning client leaves.

Ownership vs authority

The client-server and distributed authority network topologies have slight differences when it comes to ownership and authority.

• Client-server: A client can own a spawned NetworkObject but the server always maintains spawn authority over the NetworkObject. Ownership only provides the owning client authority over NetworkVariables (with write permissions), any NetworkTransform configured for owner authority, and can be used to send an RPC that targets the owner.
• Distributed authority: If a client owns a NetworkObject it becomes the "over-all" authority of that NetworkObject. This means the owning client has spawn/de-spawn authority, write permissions to NetworkVariables (associated with the owned NetworkObject), the motion authority (if the NetworkObject has any NetworkTransforms), and the owning client can change the ownership permissions flags.

The following methods change their behavior based on the network topology being used:

This, except one day Noel will learn that it's 'overall' not 'over-all'

NetworkObject.Spawn

• Client-Server: The server defaults as the owner of this spawned object.
• Distributed authority: The client invoking this method becomes the owner of the spawned object.

NetworkObject.SpawnWithOwnership

• Client-Server: The client identifier passed in as a parameter defines who the owner will be.
• Distributed authority: It is not recommended to use this method when using distributed authority if there are initial settings you want applied when spawning the new instance. For this scenario, it is recommended to use NetworkObject.Spawn, allow the settings to be applied locally, and then use NetworkObject.ChangeOwnership.

I moved SpawnWithOwnership to the bottom of the page. That way ChangeOwnership has a higher prominence than SpawnWithOwnership, hopefully leading to fewer SpawnAuthority issues.

///

private void OnOwnershipRequestResponse(NetworkObject.OwnershipRequestResponseStatus ownershipRequestResponseStatus)
{
    switch (ownershipRequestResponseStatus)
    {
        case NetworkObject.OwnershipRequestResponseStatus.Approved:
            {
                // OnOwnershipChanged and OnGainedOwnership is invoked on the client requesting side.
                // OnOwnershipChanged and OnLostOwnership is invoked on the previous owning client side.
                break;
            }
        case NetworkObject.OwnershipRequestResponseStatus.RequestInProgress:
            {
                // Another client already has a request pending.
                break;
            }
        case NetworkObject.OwnershipRequestResponseStatus.CannotRequest:
            {
                // Cannot request means RequestRequired is no longer a permission of this NetworkObject.
                // The owning client changed while the request was being sent.
                break;
            }
        case NetworkObject.OwnershipRequestResponseStatus.Denied:
            {
                // The owning client denied the request.
                break;
            }
        case NetworkObject.OwnershipRequestResponseStatus.Locked:
            {
                // Ownership has been locked by the owning client.
                break;
            }
    }
}

public override void OnNetworkDespawn()
{
    NetworkObject.OnOwnershipRequestResponse -= OnOwnershipRequestResponse;
    base.OnNetworkDespawn();
}

}

NetworkObject.SpawnWithOwnership(clientId);

owner of the object can always parent the object under any other spawned NetworkObject (owned or not).

Just remove the space:

Ownership provides client-side reactivity. By giving individual clients ownership

|-----------------------------------|----------|-------|
|Spawn/Despawn objects* |Yes |No |
|Change Ownership |Yes |No |
|Move transform** |No |Yes|
|Update NetworkVariables*** |Yes |No |
|Synchronize late joining clients |Yes |No |
|Update object parenting**** |Yes |No |

*The authority when using client-server will always be the server.
**Only when a NetworkTransform's authority mode is set to owner.
***This default behaviour can be changed using the NetworkVariableWritePermission.Owner
****This default behaviour can be changed by setting NetworkObject.AllowOwnerToParent

This, but 'behavior' rather than 'behaviour'

This, but 'behavior' rather than 'behaviour'